Use updated bullseye sysroot with fixed symlinks #200
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 23, 2025
martin4861
added a commit
to swift-nav/swift-toolchains
that referenced
this pull request
Oct 27, 2025
I ran a comparison of the chromium's sysroots with ours and found out, that symlinks look differently, e.g. - chromium: `libutil.so -> ../../..//lib/x86_64-linux-gnu/libutil.so.1` - ours (before this change): `libutil.so -> /lib/x86_64-linux-gnu/libutil.so.1` This might have worked in the past with Bazel 7, but with Bazel 8 in some situations (maybe due to Bazel 8's stricter sandboxing) it just fails. I was not able to reproduce it locally, it only happens in CI with enabled Bazel Cache. This change enables the relative symlink handling instead of using absolute paths and syncs with the upstream script of the chromium project. (`lapack` and `blas` seem to be in the correct shape: `liblapack.a -> ./lapack/liblapack.a`) Tested in swift-nav/rules_swiftnav#200 (see testplan in PR description)
martin4861
force-pushed
the
martin4861/investigate-bazel8-x86_64-sysroots-linker-failures
branch
from
cb138ac to
595c9f3
Compare
…e-bazel8-x86_64-sysroots-linker-failures
martin4861
force-pushed
the
martin4861/investigate-bazel8-x86_64-sysroots-linker-failures
branch
from
ce4af36 to
a60a311
Compare
martin4861
force-pushed
the
martin4861/investigate-bazel8-x86_64-sysroots-linker-failures
branch
2 times, most recently
from
0b401b0 to
8a7974d
Compare
martin4861
force-pushed
the
martin4861/investigate-bazel8-x86_64-sysroots-linker-failures
branch
from
8a7974d to
b589be5
Compare
martin4861
deleted the
martin4861/investigate-bazel8-x86_64-sysroots-linker-failures
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use the updated sysroots of swift-nav/swift-toolchains#27 for fixed symlinks.
Tested ✅